Skip to main content

IoT Idle Time

IOT IDLE TIME​

note

This screen is used to record idle reasons for machine stop periods by selecting a machine timeline segment and entering reason-wise time split.

1. Open IoT Idle Time Screen​

  1. Go to Production and Quality
  2. Open Operation
  3. Click IoT Idle Time

2. What This Screen Shows​

This screen has three main parts:

  1. Filter area: Machine, From Date/Time, To Date/Time, quick range buttons (4h, 8h, 24h)
  2. Timeline area: Machine status blocks shown by color for the selected time period
  3. Idle Reason entry area: Opens after selecting one status block from the timeline

3. Status Color Guide (Operator View)​

tip

Use color first, then open details.

  • 🟢 Operate: Machine is running and production is active.
  • 🟠 Suspend: Temporary pause. Machine is waiting and can continue.
  • 🟡 Stop: Work ended for that cycle. Machine is idle now.
  • 🔴 Alarm: Problem detected. Needs attention before continue.
  • ⚪ Disconnect: Machine is offline / data not coming.
  • 🟣 Emergency: Emergency stop is active for safety.

4. Search and Load Timeline​

  1. Select Machine
  2. Select From date/time
  3. Select To date/time
  4. Click Apply

Validations:

  • Machine is mandatory
  • From and To are mandatory
  • To must be later than From
  • Maximum allowed range is 24 hours

If data is not available for the selected period, the screen shows a no-data message.

5. Select a Segment and Start Entry​

  1. Click a required status block in the timeline
  2. Selected segment details appear in the entry card:
    • Machine
    • Status
    • Start time
    • End time
    • Duration

You can enter reasons only for these statuses:

  • Stop
  • Suspend
  • Alarm

For other statuses, entry is blocked with message.

6. How to Enter Idle Reasons​

In the reason table, each row has:

  • Idle Reason (search + single select)
  • From Time
  • To Time
  • Mins

Entry flow:

  1. Select reason
  2. Enter minutes
  3. System auto-calculates To Time
  4. Next row starts from previous row end time
  5. Use Add Reason to add more rows
  6. Click Save Reasons

7. Important Validations During Save​

The system checks all rows before save:

  • Reason and Mins must both be entered
  • Minutes must be greater than 0
  • Same reason cannot be selected more than once in the same segment
  • Row time range must be valid
  • Row end time cannot cross selected segment end time
  • Total entered minutes cannot be greater than selected segment duration

If any check fails, save is stopped and warning is shown.

8. Quick Meaning for Suspend and Stop​

  • 🟠 Suspend: Machine is paused for a short time and waiting to continue.
    • Example: waiting for part loading, door close, or operator action.
  • 🟡 Stop: Current work is completed and machine is now idle.
    • Example: cycle finished or manually stopped.

9. Time Display and Save Behavior​

  • Times are shown in user-readable date and time format on screen
  • On save, times are stored in standard UTC format for consistent system records

10. After Save​

After successful save:

  • Success message is shown
  • Screen refreshes automatically
  • Saved reasons appear in:
    • Selected segment hover details
    • Availability table “Saved Idle Reasons” column

11. Best Practice for Operators​

  • Use quick range first (8h recommended)
  • Select exact segment before entry
  • Complete one segment fully, then move to next
  • Keep minutes accurate to avoid save validation errors

That’s it. You can now load IoT machine status, select a stop period, and record idle reasons correctly. For further assistance, contact the Support Team.